Skip to main content

This is a new service – your feedback will help us to improve it.

Buckinghamshire Council

Tree preservation zone

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order dataset

The Rural District Council of Amersham Interim Tree Preservation Order Confirmed by Minister of Town

reference
ZZZZDVESXE748
name
The Rural District Council of Amersham Interim Tree Preservation Order Confirmed by Minister of Town
tree-preservation-order

undefined

TPO/1948/084
tree-preservation-zone-type
geometry
MULTIPOLYGON (((-0.731606 51.709234,-0.731807 51.709308,-0.731815 51.709269,-0.731819 51.709238,-0.731821 51.709172,-0.731741 51.709003,-0.731605 51.708833,-0.731424 51.708663,-0.731272 51.708524,-0.731147 51.708376,-0.731141 51.708366,-0.731140 51.708361,-0.731128 51.708238,-0.731192 51.708056,-0.731259 51.707996,-0.731165 51.707927,-0.731148 51.707910,-0.731139 51.707898,-0.731076 51.707390,-0.731055 51.707208,-0.731071 51.706829,-0.731076 51.706786,-0.731129 51.706624,-0.731188 51.706454,-0.731264 51.706259,-0.730451 51.706125,-0.729691 51.706022,-0.729589 51.706014,-0.729499 51.706013,-0.729432 51.706016,-0.728883 51.706091,-0.728532 51.706480,-0.728416 51.706601,-0.728323 51.706690,-0.727926 51.707087,-0.727832 51.707067,-0.727501 51.706983,-0.726688 51.706785,-0.726224 51.706670,-0.725319 51.706452,-0.725195 51.706595,-0.725192 51.706601,-0.725138 51.706673,-0.725124 51.706687,-0.725110 51.706704,-0.725074 51.706737,-0.725004 51.706808,-0.724944 51.706875,-0.724911 51.706918,-0.724830 51.706962,-0.724717 51.707013,-0.724654 51.707040,-0.724644 51.707043,-0.724634 51.707049,-0.724568 51.707079,-0.724511 51.707098,-0.724392 51.707141,-0.724356 51.707155,-0.724341 51.707163,-0.724309 51.707174,-0.724243 51.707200,-0.724141 51.707265,-0.724091 51.707299,-0.724063 51.707321,-0.724051 51.707334,-0.724002 51.707376,-0.723978 51.707401,-0.723969 51.707413,-0.724135 51.707484,-0.724356 51.707568,-0.724464 51.707618,-0.724540 51.707648,-0.724689 51.707699,-0.724915 51.707764,-0.724930 51.707770,-0.725084 51.707805,-0.725162 51.707830,-0.725202 51.707845,-0.725240 51.707863,-0.725312 51.707892,-0.725512 51.707987,-0.725542 51.707995,-0.725600 51.708003,-0.725643 51.708003,-0.725650 51.708000,-0.725697 51.707968,-0.725736 51.707938,-0.725761 51.707918,-0.725809 51.707873,-0.725829 51.707841,-0.725839 51.707819,-0.725852 51.707784,-0.725860 51.707751,-0.725870 51.707684,-0.725880 51.707652,-0.725902 51.707630,-0.725914 51.707625,-0.725926 51.707623,-0.725939 51.707625,-0.726052 51.707653,-0.726108 51.707664,-0.726171 51.707674,-0.726180 51.707674,-0.726319 51.707701,-0.726369 51.707709,-0.726410 51.707711,-0.726477 51.707719,-0.726514 51.707726,-0.726594 51.707746,-0.726620 51.707751,-0.726850 51.707815,-0.726893 51.707833,-0.726964 51.707855,-0.727022 51.707875,-0.727090 51.707893,-0.727155 51.707908,-0.727203 51.707922,-0.727362 51.707980,-0.727406 51.707994,-0.727456 51.708005,-0.727522 51.708008,-0.727606 51.708000,-0.727807 51.707965,-0.728035 51.707929,-0.728627 51.707945,-0.728635 51.707949,-0.728724 51.708070,-0.728733 51.708064,-0.728807 51.708083,-0.728843 51.708097,-0.728877 51.708127,-0.728925 51.708178,-0.728965 51.708209,-0.728994 51.708225,-0.729073 51.708256,-0.729092 51.708268,-0.729161 51.708348,-0.729187 51.708376,-0.729279 51.708466,-0.729382 51.708562,-0.729436 51.708609,-0.729466 51.708633,-0.729621 51.708752,-0.729959 51.708856,-0.730054 51.708880,-0.730195 51.708881,-0.730348 51.708886,-0.730465 51.708894,-0.730906 51.709011,-0.731092 51.709055,-0.731299 51.709100,-0.731606 51.709234)))
point
POINT (-0.72861 51.707412)
notes
entry-date
2010-02-18
start-date
2010-02-18
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The Tree preservation zone guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that covers this zone.

How to improve Buckinghamshire Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL